Use data driven testing #4 - #6

This help separate more complex tests from the ones that can be entirely
data-driven.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Test all attributes from contenttype.Type object by adding a new
to_dict() function and enhancing the FileTypeTest with all these
attributes. At test time, test all attributes but check only with
startswith() for text attributes rather than full equality.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

This was done by collecting the list of touched files (with a temp
override of get_test_loc() ) then touch empty yaml files and
regenerating the tests. Finally the yaml files have been hand reviewed
for correctness.

All tests with complex expectations have been kept as-is and not
migrated to data-driven tests


Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>